home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19970626-19970929
/
000027_news@newsmaster….columbia.edu _Mon Jul 7 06:26:39 1997.msg
< prev
next >
Wrap
Internet Message Format
|
1997-09-28
|
3KB
Return-Path: <news@newsmaster.cc.columbia.edu>
Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id GAA14730
for <kermit.misc@watsun.cc.columbia.edu>; Mon, 7 Jul 1997 06:26:39 -0400 (EDT)
Received: (from news@localhost)
by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id GAA12138
for kermit.misc@watsun; Mon, 7 Jul 1997 06:26:38 -0400 (EDT)
Path: news.columbia.edu!panix!howland.erols.net!news.mathworks.com!uunet!in1.uu.net!204.255.96.40!intex.net!not-for-mail
From: achalk@intex.net (Andrew Chalk)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: File transfer echo problem
Date: Mon, 07 Jul 1997 09:23:34 GMT
Organization: Intex.Net (http://www.intex.net/)
Lines: 39
Message-ID: <5pqcsu$hi1$1@alcor.nstar.net>
References: <5poa33$t65$1@alcor.nstar.net> <5pof2j$og7$1@newsmaster.cc.columbia.edu>
NNTP-Posting-Host: pppa020.nstar.net
X-Newsreader: Forte Free Agent v0.55
Xref: news.columbia.edu comp.protocols.kermit.misc:7277
fdc@watsun.cc.columbia.edu (Frank da Cruz) wrote:
>In article <5poa33$t65$1@alcor.nstar.net>,
>Andrew Chalk <achalk@intex.net> wrote:
>: I am using a micro to communicate from a kermit implementation that I
>: wrote to Kermit-TSO v4.0 (88/3/14). When I use the RECEIVE <filename>
>: command and send my SEND-INIT packet, the mainframe ECHOS BACK the
>: SEND-INIT packet, and then sends the expected ACK. In fact, when I
>: modified my code to handle this i found that the mainframe echoes back
>: EVERY PACKET I send, including the 'D' (DATA) packets before returning
>: the expected response?
>:
>: Is this a bug in Kermit-TSO or a setting on the mainframe. It
>: certainly is strange!
>:
>And through what kind of device are you accessing the mainframe?
>Evidently it is some sort of 3270 protocol converter that has not been
>put into transparent mode. You should install the current version of
>IBM mainframe Kermit (4.3.1), since it has a better chance of detecting
>the kind of protocol converter and putting it into transparent mode
>automatically. If that doesn't work, read the IBM Mainframe Kermit
>manual on this topic:
> ftp://kermit.columbia.edu/kermit/b/iktker.{ps,doc}
>In the worst case, you've got a 3270 protocol converter that does not
>support transparent mode, and so your Kermit version must cope with the
>echoes and other phenomena (line wrapping, etc).
>- Frank
Many thanks for the information Frank. This is at a customer's site,
so I will pass it on.
I modified my Kermit implementation and it now works with this 3270
(or other) device.
Regards.